[INFO] fetching crate rant 4.0.0-alpha.22...
[INFO] building rant-4.0.0-alpha.22 against master#ff34b919075f35a1787659e9c448a34b06bab8de for issue-85264
[INFO] extracting crate rant 4.0.0-alpha.22 into /workspace/builds/worker-14/source
[INFO] validating manifest of crates.io crate rant 4.0.0-alpha.22 on toolchain ff34b919075f35a1787659e9c448a34b06bab8de
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+ff34b919075f35a1787659e9c448a34b06bab8de" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate rant 4.0.0-alpha.22
[INFO] finished tweaking crates.io crate rant 4.0.0-alpha.22
[INFO] tweaked toml for crates.io crate rant 4.0.0-alpha.22 written to /workspace/builds/worker-14/source/Cargo.toml
[INFO] crate crates.io crate rant 4.0.0-alpha.22 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+ff34b919075f35a1787659e9c448a34b06bab8de" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:20528e8c29e4536546f0102ce88568b16ea7538393a33fcca951030f7af10457" "/opt/rustwide/cargo-home/bin/cargo" "+ff34b919075f35a1787659e9c448a34b06bab8de" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 5cf08a4b3f5281f2079cbfcd71c85fac412775c4955cd33a7bc357cf0bcbb8b5
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] running `Command { std: "docker" "start" "-a" "5cf08a4b3f5281f2079cbfcd71c85fac412775c4955cd33a7bc357cf0bcbb8b5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "5cf08a4b3f5281f2079cbfcd71c85fac412775c4955cd33a7bc357cf0bcbb8b5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "5cf08a4b3f5281f2079cbfcd71c85fac412775c4955cd33a7bc357cf0bcbb8b5", kill_on_drop: false }`
[INFO] [stdout] 5cf08a4b3f5281f2079cbfcd71c85fac412775c4955cd33a7bc357cf0bcbb8b5
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:20528e8c29e4536546f0102ce88568b16ea7538393a33fcca951030f7af10457" "/opt/rustwide/cargo-home/bin/cargo" "+ff34b919075f35a1787659e9c448a34b06bab8de" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] f2e939e835c3688a470cad7dc2b0b3cc21e2b072ef0295ae7afde887468c7fdd
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] running `Command { std: "docker" "start" "-a" "f2e939e835c3688a470cad7dc2b0b3cc21e2b072ef0295ae7afde887468c7fdd", kill_on_drop: false }`
[INFO] [stderr]    Compiling libc v0.2.73
[INFO] [stderr]    Compiling getrandom v0.2.1
[INFO] [stderr]    Compiling unicode-xid v0.2.1
[INFO] [stderr]    Compiling cfg-if v1.0.0
[INFO] [stderr]    Compiling syn v1.0.33
[INFO] [stderr]    Compiling beef v0.5.0
[INFO] [stderr]    Compiling smallvec v1.6.1
[INFO] [stderr]    Compiling line-col v0.2.1
[INFO] [stderr]    Compiling cervine v0.0.6
[INFO] [stderr]    Compiling indexmap v1.6.1
[INFO] [stderr]    Compiling smartstring v0.2.6
[INFO] [stderr]    Compiling cast v0.2.3
[INFO] [stderr]    Compiling proc-macro2 v1.0.18
[INFO] [stderr]    Compiling quote v1.0.7
[INFO] [stderr]    Compiling quickscope v0.1.6
[INFO] [stderr]    Compiling rand_core v0.6.1
[INFO] [stderr]    Compiling rand_chacha v0.3.0
[INFO] [stderr]    Compiling rand_xoshiro v0.6.0
[INFO] [stderr]    Compiling rand v0.8.3
[INFO] [stderr]    Compiling logos-derive v0.12.0
[INFO] [stderr]    Compiling logos v0.12.0
[INFO] [stderr]    Compiling rant v4.0.0-alpha.22 (/opt/rustwide/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 28.68s
[INFO] running `Command { std: "docker" "inspect" "f2e939e835c3688a470cad7dc2b0b3cc21e2b072ef0295ae7afde887468c7fdd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f2e939e835c3688a470cad7dc2b0b3cc21e2b072ef0295ae7afde887468c7fdd", kill_on_drop: false }`
[INFO] [stdout] f2e939e835c3688a470cad7dc2b0b3cc21e2b072ef0295ae7afde887468c7fdd
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:20528e8c29e4536546f0102ce88568b16ea7538393a33fcca951030f7af10457" "/opt/rustwide/cargo-home/bin/cargo" "+ff34b919075f35a1787659e9c448a34b06bab8de" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 355a6b87d69f4ec8da136f442c5e95434ce3f07d4e241061886bdd6604b39684
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] running `Command { std: "docker" "start" "-a" "355a6b87d69f4ec8da136f442c5e95434ce3f07d4e241061886bdd6604b39684", kill_on_drop: false }`
[INFO] [stderr]    Compiling assert_matches v1.5.0
[INFO] [stderr]    Compiling rant v4.0.0-alpha.22 (/opt/rustwide/workdir)
[INFO] [stdout] error: couldn't read tests/sources/block/defer_block.rant: No such file or directory (os error 2)
[INFO] [stdout]   --> tests/runtime_tests.rs:29:31
[INFO] [stdout]    |
[INFO] [stdout] 29 |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]    |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 82 |   test_rant_file!("sources/block/defer_block.rant");
[INFO] [stdout]    |   -------------------------------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/func/func_with_variadic_star.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 127 | /   test_rant_file!(
[INFO] [stdout] 128 | |     "sources/func/func_with_variadic_star.rant",
[INFO] [stdout] 129 | |     "\na\na b\na b c\na b c d"
[INFO] [stdout] 130 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/func/func_with_variadic_plus.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 135 | /   test_rant_file!(
[INFO] [stdout] 136 | |     "sources/func/func_with_variadic_plus.rant",
[INFO] [stdout] 137 | |     "a\na b\na b c\na b c d"
[INFO] [stdout] 138 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/func/func_with_optional_param.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 143 | /   test_rant_file!(
[INFO] [stdout] 144 | |     "sources/func/func_with_optional_param.rant", 
[INFO] [stdout] 145 | |     "foo\nbar"
[INFO] [stdout] 146 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/override_shadowed_locals_with_multi_descope.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 176 | /   test_rant_file!(
[INFO] [stdout] 177 | |     "sources/access/override_shadowed_locals_with_multi_descope.rant",
[INFO] [stdout] 178 | |     "foo bar baz"
[INFO] [stdout] 179 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/dynamic_index_setter.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 204 | /   test_rant_file!(
[INFO] [stdout] 205 | |     "sources/access/dynamic_index_setter.rant",
[INFO] [stdout] 206 | |     "1, 2, 4"
[INFO] [stdout] 207 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/dynamic_multi_index_setter.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 212 | /   test_rant_file!(
[INFO] [stdout] 213 | |     "sources/access/dynamic_multi_index_setter.rant",
[INFO] [stdout] 214 | |     "1, 2, 4, 4, 5, 6"
[INFO] [stdout] 215 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/closure/closure_capture_var.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 220 | /   test_rant_file!(
[INFO] [stdout] 221 | |     "sources/closure/closure_capture_var.rant",
[INFO] [stdout] 222 | |     "foo"
[INFO] [stdout] 223 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/closure/closure_capture_arg.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 228 | /   test_rant_file!(
[INFO] [stdout] 229 | |     "sources/closure/closure_capture_arg.rant",
[INFO] [stdout] 230 | |     "foo"
[INFO] [stdout] 231 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/closure/closure_mutate_captured_value.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 236 | /   test_rant_file!(
[INFO] [stdout] 237 | |     "sources/closure/closure_mutate_captured_value.rant",
[INFO] [stdout] 238 | |     "0 1 2 3"
[INFO] [stdout] 239 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/filter_with_native_predicate.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 244 | /   test_rant_file!(
[INFO] [stdout] 245 | |     "sources/collections/filter_with_native_predicate.rant",
[INFO] [stdout] 246 | |     "1, 3, 5, 7, 9"
[INFO] [stdout] 247 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/filter_with_user_predicate.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 252 | /   test_rant_file!(
[INFO] [stdout] 253 | |     "sources/collections/filter_with_user_predicate.rant",
[INFO] [stdout] 254 | |     "1, 3, 5, 7, 9"
[INFO] [stdout] 255 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/map_with_native_callback.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 260 | /   test_rant_file!(
[INFO] [stdout] 261 | |     "sources/collections/map_with_native_callback.rant",
[INFO] [stdout] 262 | |     "-1, -2, -3, -4, -5, -6, -7, -8, -9, -10"
[INFO] [stdout] 263 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/map_with_user_callback.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 268 | /   test_rant_file!(
[INFO] [stdout] 269 | |     "sources/collections/map_with_user_callback.rant",
[INFO] [stdout] 270 | |     "-1, -2, -3, -4, -5, -6, -7, -8, -9, -10"
[INFO] [stdout] 271 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/zip_with_native_callback.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 276 | /   test_rant_file!(
[INFO] [stdout] 277 | |     "sources/collections/zip_with_native_callback.rant",
[INFO] [stdout] 278 | |     "5, 7, 9"
[INFO] [stdout] 279 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/zip_with_user_callback.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 284 | /   test_rant_file!(
[INFO] [stdout] 285 | |     "sources/collections/zip_with_user_callback.rant",
[INFO] [stdout] 286 | |     "5, 7, 9"
[INFO] [stdout] 287 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/func/func_percolation.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 292 | /   test_rant_file!(
[INFO] [stdout] 293 | |     "sources/func/func_percolation.rant",
[INFO] [stdout] 294 | |     "global\nlocal\nvery local"
[INFO] [stdout] 295 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/anonymous/anon_getter.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 300 | /   test_rant_file!(
[INFO] [stdout] 301 | |     "sources/anonymous/anon_getter.rant",
[INFO] [stdout] 302 | |     "foo bar"
[INFO] [stdout] 303 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/anonymous/dynamic_anon_getter.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 308 | /   test_rant_file!(
[INFO] [stdout] 309 | |     "sources/anonymous/dynamic_anon_getter.rant",
[INFO] [stdout] 310 | |     "6"
[INFO] [stdout] 311 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/anonymous/anon_setter.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 316 | /   test_rant_file!(
[INFO] [stdout] 317 | |     "sources/anonymous/anon_setter.rant",
[INFO] [stdout] 318 | |     "baz qux"
[INFO] [stdout] 319 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/anonymous/dynamic_anon_setter.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | /   test_rant_file!(
[INFO] [stdout] 325 | |     "sources/anonymous/dynamic_anon_setter.rant",
[INFO] [stdout] 326 | |     "7"
[INFO] [stdout] 327 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/inv_index_get.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | /   test_rant_file!(
[INFO] [stdout] 333 | |     "sources/access/inv_index_get.rant",
[INFO] [stdout] 334 | |     "3, 2, 1"
[INFO] [stdout] 335 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/inv_index_set.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 340 | /   test_rant_file!(
[INFO] [stdout] 341 | |     "sources/access/inv_index_set.rant",
[INFO] [stdout] 342 | |     "4, 5, 6"
[INFO] [stdout] 343 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/func/function_composition.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 348 | /   test_rant_file!(
[INFO] [stdout] 349 | |     "sources/func/function_composition.rant",
[INFO] [stdout] 350 | |     "the fox the dog"
[INFO] [stdout] 351 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/func/function_composition_callback.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 356 | /   test_rant_file!(
[INFO] [stdout] 357 | |     "sources/func/function_composition_callback.rant",
[INFO] [stdout] 358 | |     "foo bar"
[INFO] [stdout] 359 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/getter_fallback_from_var.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 364 | /   test_rant_file!(
[INFO] [stdout] 365 | |     "sources/access/getter_fallback_from_var.rant",
[INFO] [stdout] 366 | |     "123, fallback"
[INFO] [stdout] 367 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/getter_fallback_from_index.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 372 | /   test_rant_file!(
[INFO] [stdout] 373 | |     "sources/access/getter_fallback_from_index.rant",
[INFO] [stdout] 374 | |     "foo, bar, baz, oops"
[INFO] [stdout] 375 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/access/getter_fallback_from_key.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:37:31
[INFO] [stdout]     |
[INFO] [stdout] 37  |       let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 380 | /   test_rant_file!(
[INFO] [stdout] 381 | |     "sources/access/getter_fallback_from_key.rant",
[INFO] [stdout] 382 | |     "foo, bar, baz, oops"
[INFO] [stdout] 383 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/top_level_return.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 388 |   test_rant_file!("sources/charms/top_level_return.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/func_return_output.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 393 |   test_rant_file!("sources/charms/func_return_output.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/func_return_value.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 398 |   test_rant_file!("sources/charms/func_return_value.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/rep_continue_output.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 403 |   test_rant_file!("sources/charms/rep_continue_output.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/rep_continue_value.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 408 |   test_rant_file!("sources/charms/rep_continue_value.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/rep_break_output.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 413 |   test_rant_file!("sources/charms/rep_break_output.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/rep_break_value.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 418 |   test_rant_file!("sources/charms/rep_break_value.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/charms/weight_all_zero.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 423 |   test_rant_file!("sources/charms/weight_all_zero.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/assert/assert_pass.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 428 |   test_rant_file!("sources/assert/assert_pass.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/assert/assert_fail.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:21:31
[INFO] [stdout]     |
[INFO] [stdout] 21  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 433 |   test_rant_file!("sources/assert/assert_fail.rant" raises AssertError);
[INFO] [stdout]     |   ---------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/math/min.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 438 |   test_rant_file!("sources/math/min.rant");
[INFO] [stdout]     |   ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/math/max.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 443 |   test_rant_file!("sources/math/max.rant");
[INFO] [stdout]     |   ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/list/full.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 448 |   test_rant_file!("sources/slice/list/full.rant");
[INFO] [stdout]     |   ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/list/between_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 453 |   test_rant_file!("sources/slice/list/between_static.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/list/from_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 458 |   test_rant_file!("sources/slice/list/from_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/list/to_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 463 |   test_rant_file!("sources/slice/list/to_static.rant");
[INFO] [stdout]     |   ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/list/between_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 468 |   test_rant_file!("sources/slice/list/between_dynamic.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/list/from_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 473 |   test_rant_file!("sources/slice/list/from_dynamic.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/list/to_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 478 |   test_rant_file!("sources/slice/list/to_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/block/full.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 483 |   test_rant_file!("sources/slice/block/full.rant");
[INFO] [stdout]     |   ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/block/between_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 488 |   test_rant_file!("sources/slice/block/between_static.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/block/from_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 493 |   test_rant_file!("sources/slice/block/from_static.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/block/to_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 498 |   test_rant_file!("sources/slice/block/to_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/block/between_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 503 |   test_rant_file!("sources/slice/block/between_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/block/from_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 508 |   test_rant_file!("sources/slice/block/from_dynamic.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/block/to_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 513 |   test_rant_file!("sources/slice/block/to_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/string/full.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 518 |   test_rant_file!("sources/slice/string/full.rant");
[INFO] [stdout]     |   -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/string/between_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 523 |   test_rant_file!("sources/slice/string/between_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/string/from_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 528 |   test_rant_file!("sources/slice/string/from_static.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/string/to_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 533 |   test_rant_file!("sources/slice/string/to_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/string/between_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 538 |   test_rant_file!("sources/slice/string/between_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/string/from_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 543 |   test_rant_file!("sources/slice/string/from_dynamic.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/string/to_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 548 |   test_rant_file!("sources/slice/string/to_dynamic.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/range/full.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 553 |   test_rant_file!("sources/slice/range/full.rant");
[INFO] [stdout]     |   ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/range/between_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 558 |   test_rant_file!("sources/slice/range/between_static.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/range/from_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 563 |   test_rant_file!("sources/slice/range/from_static.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/range/to_static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 568 |   test_rant_file!("sources/slice/range/to_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/range/between_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 573 |   test_rant_file!("sources/slice/range/between_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/range/from_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 578 |   test_rant_file!("sources/slice/range/from_dynamic.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/slice/range/to_dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 583 |   test_rant_file!("sources/slice/range/to_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/splice/static.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 588 |   test_rant_file!("sources/splice/static.rant");
[INFO] [stdout]     |   ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/splice/dynamic.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 593 |   test_rant_file!("sources/splice/dynamic.rant");
[INFO] [stdout]     |   ----------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/modules/require.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 598 |   test_rant_file!("sources/modules/require.rant");
[INFO] [stdout]     |   ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/spread/spread_all.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 603 |   test_rant_file!("sources/spread/spread_all.rant");
[INFO] [stdout]     |   -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/spread/spread_inner.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 608 |   test_rant_file!("sources/spread/spread_inner.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/spread/spread_left.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 613 |   test_rant_file!("sources/spread/spread_left.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/spread/spread_right.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 618 |   test_rant_file!("sources/spread/spread_right.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/spread/spread_multi.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 623 |   test_rant_file!("sources/spread/spread_multi.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/spread/spread_variadic_star.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 628 |   test_rant_file!("sources/spread/spread_variadic_star.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/spread/spread_variadic_plus.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 633 |   test_rant_file!("sources/spread/spread_variadic_plus.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/const/const_define.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 638 |   test_rant_file!("sources/const/const_define.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/const/const_function.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 643 |   test_rant_file!("sources/const/const_function.rant");
[INFO] [stdout]     |   ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/const/redef_var_with_const.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 648 |   test_rant_file!("sources/const/redef_var_with_const.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/const/const_shadow.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 653 |   test_rant_file!("sources/const/const_shadow.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/const/reassign_const.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:21:31
[INFO] [stdout]     |
[INFO] [stdout] 21  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 658 |   test_rant_file!("sources/const/reassign_const.rant" raises InvalidAccess);
[INFO] [stdout]     |   -------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/const/reassign_const_parent.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:21:31
[INFO] [stdout]     |
[INFO] [stdout] 21  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 663 |   test_rant_file!("sources/const/reassign_const_parent.rant" raises InvalidAccess);
[INFO] [stdout]     |   --------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/list_autoconcat.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 668 |   test_rant_file!("sources/collections/list_autoconcat.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/list_autoconcat_repeater.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 673 |   test_rant_file!("sources/collections/list_autoconcat_repeater.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/collections/map_autoconcat.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 678 |   test_rant_file!("sources/collections/map_autoconcat.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_one.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 683 |   test_rant_file!("sources/temporal/temporal_one.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_one_mixed.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 688 |   test_rant_file!("sources/temporal/temporal_one_mixed.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_two_samesize.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 693 |   test_rant_file!("sources/temporal/temporal_two_samesize.rant");
[INFO] [stdout]     |   --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_two_samesize_mixed.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 698 |   test_rant_file!("sources/temporal/temporal_two_samesize_mixed.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_two_samesize_sync.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 703 |   test_rant_file!("sources/temporal/temporal_two_samesize_sync.rant");
[INFO] [stdout]     |   -------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_two_diffsize.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 708 |   test_rant_file!("sources/temporal/temporal_two_diffsize.rant");
[INFO] [stdout]     |   --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_two_diffsize_mixed.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 713 |   test_rant_file!("sources/temporal/temporal_two_diffsize_mixed.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/temporal/temporal_comp_temporal.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 718 |   test_rant_file!("sources/temporal/temporal_comp_temporal.rant");
[INFO] [stdout]     |   ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/range/range_forward.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 723 |   test_rant_file!("sources/range/range_forward.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/range/range_reverse.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 728 |   test_rant_file!("sources/range/range_reverse.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/range/range_forward_step_divisible.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 733 |   test_rant_file!("sources/range/range_forward_step_divisible.rant");
[INFO] [stdout]     |   ------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/range/range_reverse_step_divisible.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 738 |   test_rant_file!("sources/range/range_reverse_step_divisible.rant");
[INFO] [stdout]     |   ------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/range/range_forward_step_indivisible.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 743 |   test_rant_file!("sources/range/range_forward_step_indivisible.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read tests/sources/range/range_reverse_step_indivisible.rant: No such file or directory (os error 2)
[INFO] [stdout]    --> tests/runtime_tests.rs:29:31
[INFO] [stdout]     |
[INFO] [stdout] 29  |     let pgm = r.compile_quiet(include_str!($src_path)).expect("failed to compile program");
[INFO] [stdout]     |                               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 748 |   test_rant_file!("sources/range/range_reverse_step_indivisible.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 52 |   test_rant!("", "");
[INFO] [stdout]    |   ------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 57 |   test_rant!("foo", "foo");
[INFO] [stdout]    |   ------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 62 |   test_rant!("foo bar", "foo bar");
[INFO] [stdout]    |   --------------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 67 |   test_rant!("_{test}", "");
[INFO] [stdout]    |   -------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 72 |   test_rant!("{test}", "test");
[INFO] [stdout]    |   ----------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 77 |   test_rant!("[rep:10]{a}", "aaaaaaaaaa");
[INFO] [stdout]    |   ---------------------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:30:5
[INFO] [stdout]    |
[INFO] [stdout] 30 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 82 |   test_rant_file!("sources/block/defer_block.rant");
[INFO] [stdout]    |   -------------------------------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 87 |   test_rant!(r#"[rep:10][sep:\s]{a}"#, "a a a a a a a a a a");
[INFO] [stdout]    |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 92 |   test_rant!(r#"[rep:10][sep:[?]{b}]{a}"#, "abababababababababa");
[INFO] [stdout]    |   ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]   --> tests/runtime_tests.rs:46:5
[INFO] [stdout]    |
[INFO] [stdout] 46 |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]    |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 97 |   test_rant!(r#"[rep:16][sel:[mksel:forward]]{a|b|c|d|e|f|g|h}"#, "abcdefghabcdefgh");
[INFO] [stdout]    |   ------------------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]   --> tests/runtime_tests.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 | use assert_matches::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]    = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]    = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 102 |   test_rant!(r#"[rep:16][sel:[mksel:reverse]]{a|b|c|d|e|f|g|h}"#, "hgfedcbahgfedcba");
[INFO] [stdout]     |   ------------------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 107 |   test_rant!(r#"[rep:16][sel:[mksel:ping]]{a|b|c|d|e|f|g|h}"#, "abcdefghgfedcbab");
[INFO] [stdout]     |   --------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 112 |   test_rant!(r#"[rep:16][sel:[mksel:pong]]{a|b|c|d|e|f|g|h}"#, "hgfedcbabcdefghg");
[INFO] [stdout]     |   --------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 117 |   test_rant!(r#"[$example-func]{test}[example-func]"#, "test");
[INFO] [stdout]     |   ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 122 |   test_rant!(r#"[$square:x]{[mul:<x>;<x>]} [square:3]"#, "9");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 127 | /   test_rant_file!(
[INFO] [stdout] 128 | |     "sources/func/func_with_variadic_star.rant",
[INFO] [stdout] 129 | |     "\na\na b\na b c\na b c d"
[INFO] [stdout] 130 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 135 | /   test_rant_file!(
[INFO] [stdout] 136 | |     "sources/func/func_with_variadic_plus.rant",
[INFO] [stdout] 137 | |     "a\na b\na b c\na b c d"
[INFO] [stdout] 138 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 143 | /   test_rant_file!(
[INFO] [stdout] 144 | |     "sources/func/func_with_optional_param.rant", 
[INFO] [stdout] 145 | |     "foo\nbar"
[INFO] [stdout] 146 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 151 |   test_rant!(r#"<$/test=foo><$test=bar><test>"#, "bar")
[INFO] [stdout]     |   ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 156 |   test_rant!(r#"<$test=foo>{<$test=bar><test>}"#, "bar")
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 161 |   test_rant!(r#"<$/example=foo><$example=bar></example>"#, "foo");
[INFO] [stdout]     |   ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 166 |   test_rant!(r#"<$/example=foo><$example=bar><^example>"#, "foo");
[INFO] [stdout]     |   ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 171 |   test_rant!(r#"<$test=foo>{<$test=bar><^test>}"#, "foo")
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 176 | /   test_rant_file!(
[INFO] [stdout] 177 | |     "sources/access/override_shadowed_locals_with_multi_descope.rant",
[INFO] [stdout] 178 | |     "foo bar baz"
[INFO] [stdout] 179 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 184 |   test_rant!(r#"<$foo; $bar> '[type:<foo>] '[type:<bar>]"#, "empty empty");
[INFO] [stdout]     |   ------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 189 |   test_rant!(r#"<$foo=8; $bar=2; $baz=[sub:<foo>;<bar>]; baz>"#, "6");
[INFO] [stdout]     |   -------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 194 |   test_rant!(r#"<$foo=bar; foo=baz; foo>"#, "baz");
[INFO] [stdout]     |   ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:46:5
[INFO] [stdout]     |
[INFO] [stdout] 46  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 199 |   test_rant!(r#"<$foo=8; $bar=2; $baz=[add:<foo>;<bar>]; baz;>"#, "10");
[INFO] [stdout]     |   ---------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 204 | /   test_rant_file!(
[INFO] [stdout] 205 | |     "sources/access/dynamic_index_setter.rant",
[INFO] [stdout] 206 | |     "1, 2, 4"
[INFO] [stdout] 207 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 212 | /   test_rant_file!(
[INFO] [stdout] 213 | |     "sources/access/dynamic_multi_index_setter.rant",
[INFO] [stdout] 214 | |     "1, 2, 4, 4, 5, 6"
[INFO] [stdout] 215 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 220 | /   test_rant_file!(
[INFO] [stdout] 221 | |     "sources/closure/closure_capture_var.rant",
[INFO] [stdout] 222 | |     "foo"
[INFO] [stdout] 223 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 228 | /   test_rant_file!(
[INFO] [stdout] 229 | |     "sources/closure/closure_capture_arg.rant",
[INFO] [stdout] 230 | |     "foo"
[INFO] [stdout] 231 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 236 | /   test_rant_file!(
[INFO] [stdout] 237 | |     "sources/closure/closure_mutate_captured_value.rant",
[INFO] [stdout] 238 | |     "0 1 2 3"
[INFO] [stdout] 239 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 244 | /   test_rant_file!(
[INFO] [stdout] 245 | |     "sources/collections/filter_with_native_predicate.rant",
[INFO] [stdout] 246 | |     "1, 3, 5, 7, 9"
[INFO] [stdout] 247 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 252 | /   test_rant_file!(
[INFO] [stdout] 253 | |     "sources/collections/filter_with_user_predicate.rant",
[INFO] [stdout] 254 | |     "1, 3, 5, 7, 9"
[INFO] [stdout] 255 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 260 | /   test_rant_file!(
[INFO] [stdout] 261 | |     "sources/collections/map_with_native_callback.rant",
[INFO] [stdout] 262 | |     "-1, -2, -3, -4, -5, -6, -7, -8, -9, -10"
[INFO] [stdout] 263 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 268 | /   test_rant_file!(
[INFO] [stdout] 269 | |     "sources/collections/map_with_user_callback.rant",
[INFO] [stdout] 270 | |     "-1, -2, -3, -4, -5, -6, -7, -8, -9, -10"
[INFO] [stdout] 271 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 276 | /   test_rant_file!(
[INFO] [stdout] 277 | |     "sources/collections/zip_with_native_callback.rant",
[INFO] [stdout] 278 | |     "5, 7, 9"
[INFO] [stdout] 279 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 284 | /   test_rant_file!(
[INFO] [stdout] 285 | |     "sources/collections/zip_with_user_callback.rant",
[INFO] [stdout] 286 | |     "5, 7, 9"
[INFO] [stdout] 287 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 292 | /   test_rant_file!(
[INFO] [stdout] 293 | |     "sources/func/func_percolation.rant",
[INFO] [stdout] 294 | |     "global\nlocal\nvery local"
[INFO] [stdout] 295 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 300 | /   test_rant_file!(
[INFO] [stdout] 301 | |     "sources/anonymous/anon_getter.rant",
[INFO] [stdout] 302 | |     "foo bar"
[INFO] [stdout] 303 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 308 | /   test_rant_file!(
[INFO] [stdout] 309 | |     "sources/anonymous/dynamic_anon_getter.rant",
[INFO] [stdout] 310 | |     "6"
[INFO] [stdout] 311 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 316 | /   test_rant_file!(
[INFO] [stdout] 317 | |     "sources/anonymous/anon_setter.rant",
[INFO] [stdout] 318 | |     "baz qux"
[INFO] [stdout] 319 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 324 | /   test_rant_file!(
[INFO] [stdout] 325 | |     "sources/anonymous/dynamic_anon_setter.rant",
[INFO] [stdout] 326 | |     "7"
[INFO] [stdout] 327 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 332 | /   test_rant_file!(
[INFO] [stdout] 333 | |     "sources/access/inv_index_get.rant",
[INFO] [stdout] 334 | |     "3, 2, 1"
[INFO] [stdout] 335 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 340 | /   test_rant_file!(
[INFO] [stdout] 341 | |     "sources/access/inv_index_set.rant",
[INFO] [stdout] 342 | |     "4, 5, 6"
[INFO] [stdout] 343 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 348 | /   test_rant_file!(
[INFO] [stdout] 349 | |     "sources/func/function_composition.rant",
[INFO] [stdout] 350 | |     "the fox the dog"
[INFO] [stdout] 351 | |   );
[INFO] [stdout]     | |____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 356 | /   test_rant_file!(
[INFO] [stdout] 357 | |     "sources/func/function_composition_callback.rant",
[INFO] [stdout] 358 | |     "foo bar"
[INFO] [stdout] 359 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 364 | /   test_rant_file!(
[INFO] [stdout] 365 | |     "sources/access/getter_fallback_from_var.rant",
[INFO] [stdout] 366 | |     "123, fallback"
[INFO] [stdout] 367 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 372 | /   test_rant_file!(
[INFO] [stdout] 373 | |     "sources/access/getter_fallback_from_index.rant",
[INFO] [stdout] 374 | |     "foo, bar, baz, oops"
[INFO] [stdout] 375 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:38:5
[INFO] [stdout]     |
[INFO] [stdout] 38  |       assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok($expected));
[INFO] [stdout]     |       ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 380 | /   test_rant_file!(
[INFO] [stdout] 381 | |     "sources/access/getter_fallback_from_key.rant",
[INFO] [stdout] 382 | |     "foo, bar, baz, oops"
[INFO] [stdout] 383 | |   )
[INFO] [stdout]     | |___- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 388 |   test_rant_file!("sources/charms/top_level_return.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 393 |   test_rant_file!("sources/charms/func_return_output.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 398 |   test_rant_file!("sources/charms/func_return_value.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 403 |   test_rant_file!("sources/charms/rep_continue_output.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 408 |   test_rant_file!("sources/charms/rep_continue_value.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 413 |   test_rant_file!("sources/charms/rep_break_output.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 418 |   test_rant_file!("sources/charms/rep_break_value.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 423 |   test_rant_file!("sources/charms/weight_all_zero.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 428 |   test_rant_file!("sources/assert/assert_pass.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:22:5
[INFO] [stdout]     |
[INFO] [stdout] 22  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Err(RuntimeError { error_type: $runtime_er...
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 433 |   test_rant_file!("sources/assert/assert_fail.rant" raises AssertError);
[INFO] [stdout]     |   ---------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 438 |   test_rant_file!("sources/math/min.rant");
[INFO] [stdout]     |   ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 443 |   test_rant_file!("sources/math/max.rant");
[INFO] [stdout]     |   ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 448 |   test_rant_file!("sources/slice/list/full.rant");
[INFO] [stdout]     |   ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 453 |   test_rant_file!("sources/slice/list/between_static.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 458 |   test_rant_file!("sources/slice/list/from_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 463 |   test_rant_file!("sources/slice/list/to_static.rant");
[INFO] [stdout]     |   ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 468 |   test_rant_file!("sources/slice/list/between_dynamic.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 473 |   test_rant_file!("sources/slice/list/from_dynamic.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 478 |   test_rant_file!("sources/slice/list/to_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 483 |   test_rant_file!("sources/slice/block/full.rant");
[INFO] [stdout]     |   ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 488 |   test_rant_file!("sources/slice/block/between_static.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 493 |   test_rant_file!("sources/slice/block/from_static.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 498 |   test_rant_file!("sources/slice/block/to_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 503 |   test_rant_file!("sources/slice/block/between_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 508 |   test_rant_file!("sources/slice/block/from_dynamic.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 513 |   test_rant_file!("sources/slice/block/to_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 518 |   test_rant_file!("sources/slice/string/full.rant");
[INFO] [stdout]     |   -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 523 |   test_rant_file!("sources/slice/string/between_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 528 |   test_rant_file!("sources/slice/string/from_static.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 533 |   test_rant_file!("sources/slice/string/to_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 538 |   test_rant_file!("sources/slice/string/between_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 543 |   test_rant_file!("sources/slice/string/from_dynamic.rant");
[INFO] [stdout]     |   ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 548 |   test_rant_file!("sources/slice/string/to_dynamic.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 553 |   test_rant_file!("sources/slice/range/full.rant");
[INFO] [stdout]     |   ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 558 |   test_rant_file!("sources/slice/range/between_static.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 563 |   test_rant_file!("sources/slice/range/from_static.rant");
[INFO] [stdout]     |   -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 568 |   test_rant_file!("sources/slice/range/to_static.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 573 |   test_rant_file!("sources/slice/range/between_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 578 |   test_rant_file!("sources/slice/range/from_dynamic.rant");
[INFO] [stdout]     |   --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 583 |   test_rant_file!("sources/slice/range/to_dynamic.rant");
[INFO] [stdout]     |   ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 588 |   test_rant_file!("sources/splice/static.rant");
[INFO] [stdout]     |   ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 593 |   test_rant_file!("sources/splice/dynamic.rant");
[INFO] [stdout]     |   ----------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 598 |   test_rant_file!("sources/modules/require.rant");
[INFO] [stdout]     |   ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 603 |   test_rant_file!("sources/spread/spread_all.rant");
[INFO] [stdout]     |   -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 608 |   test_rant_file!("sources/spread/spread_inner.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 613 |   test_rant_file!("sources/spread/spread_left.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 618 |   test_rant_file!("sources/spread/spread_right.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 623 |   test_rant_file!("sources/spread/spread_multi.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 628 |   test_rant_file!("sources/spread/spread_variadic_star.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 633 |   test_rant_file!("sources/spread/spread_variadic_plus.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 638 |   test_rant_file!("sources/const/const_define.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 643 |   test_rant_file!("sources/const/const_function.rant");
[INFO] [stdout]     |   ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 648 |   test_rant_file!("sources/const/redef_var_with_const.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 653 |   test_rant_file!("sources/const/const_shadow.rant");
[INFO] [stdout]     |   --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:22:5
[INFO] [stdout]     |
[INFO] [stdout] 22  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Err(RuntimeError { error_type: $runtime_er...
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 658 |   test_rant_file!("sources/const/reassign_const.rant" raises InvalidAccess);
[INFO] [stdout]     |   -------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:22:5
[INFO] [stdout]     |
[INFO] [stdout] 22  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Err(RuntimeError { error_type: $runtime_er...
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 663 |   test_rant_file!("sources/const/reassign_const_parent.rant" raises InvalidAccess);
[INFO] [stdout]     |   --------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 668 |   test_rant_file!("sources/collections/list_autoconcat.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 673 |   test_rant_file!("sources/collections/list_autoconcat_repeater.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 678 |   test_rant_file!("sources/collections/map_autoconcat.rant");
[INFO] [stdout]     |   ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 683 |   test_rant_file!("sources/temporal/temporal_one.rant");
[INFO] [stdout]     |   ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 688 |   test_rant_file!("sources/temporal/temporal_one_mixed.rant");
[INFO] [stdout]     |   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 693 |   test_rant_file!("sources/temporal/temporal_two_samesize.rant");
[INFO] [stdout]     |   --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 698 |   test_rant_file!("sources/temporal/temporal_two_samesize_mixed.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 703 |   test_rant_file!("sources/temporal/temporal_two_samesize_sync.rant");
[INFO] [stdout]     |   -------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 708 |   test_rant_file!("sources/temporal/temporal_two_diffsize.rant");
[INFO] [stdout]     |   --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 713 |   test_rant_file!("sources/temporal/temporal_two_diffsize_mixed.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 718 |   test_rant_file!("sources/temporal/temporal_comp_temporal.rant");
[INFO] [stdout]     |   ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 723 |   test_rant_file!("sources/range/range_forward.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 728 |   test_rant_file!("sources/range/range_reverse.rant");
[INFO] [stdout]     |   ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 733 |   test_rant_file!("sources/range/range_forward_step_divisible.rant");
[INFO] [stdout]     |   ------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 738 |   test_rant_file!("sources/range/range_reverse_step_divisible.rant");
[INFO] [stdout]     |   ------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 743 |   test_rant_file!("sources/range/range_forward_step_indivisible.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution)
[INFO] [stdout]    --> tests/runtime_tests.rs:30:5
[INFO] [stdout]     |
[INFO] [stdout] 30  |     assert_matches!(r.run(&pgm).map(|output| output.to_string()).as_ref().map(|o| o.as_str()), Ok(_));
[INFO] [stdout]     |     ^^^^^^^^^^^^^^ ambiguous name
[INFO] [stdout] ...
[INFO] [stdout] 748 |   test_rant_file!("sources/range/range_reverse_step_indivisible.rant");
[INFO] [stdout]     |   --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `assert_matches` could refer to a macro from prelude
[INFO] [stdout] note: `assert_matches` could also refer to the macro imported here
[INFO] [stdout]    --> tests/runtime_tests.rs:11:5
[INFO] [stdout]     |
[INFO] [stdout] 11  | use assert_matches::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `assert_matches` to disambiguate
[INFO] [stdout]     = help: or use `crate::assert_matches` to refer to this macro unambiguously
[INFO] [stdout]     = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 225 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0659`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `rant`
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stderr] error: build failed
[INFO] running `Command { std: "docker" "inspect" "355a6b87d69f4ec8da136f442c5e95434ce3f07d4e241061886bdd6604b39684", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "355a6b87d69f4ec8da136f442c5e95434ce3f07d4e241061886bdd6604b39684", kill_on_drop: false }`
[INFO] [stdout] 355a6b87d69f4ec8da136f442c5e95434ce3f07d4e241061886bdd6604b39684
